docs: point the issue chooser at the platform adapter vote - #781
Conversation
The four platform-adapter epics - wolfSSL (#691), lwIP Sockets (#692), LittleFS (#693) and Zephyr (#694) - are deliberately left unmilestoned, so that a thumbs-up on one carries real signal about demand rather than being a reaction to something already committed. Nothing told a reader that. A third contact link sends them to those issues, filtered to the platform label and sorted by reactions, so the list arrives already ordered by demand and the most-wanted adapter is the first thing seen. It sits below the security routes and above commercial licensing: the free way to influence what gets built should come before the paid one. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. WalkthroughThe issue template now includes a contact link for voting on platform adapter candidates. The link targets open, platform-labelled issues sorted by reactions. ChangesPlatform adapter voting
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized change adds an issue-chooser link for voting on platform adapter demand without affecting code, existing templates, or production behavior; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
☀️ Quality Summary Created by Quality Monitor v4.15.0 (#82d77af). More details are shown in the GitHub Checks Result. |
1 participant
Purpose
The four platform-adapter epics — wolfSSL (#691), lwIP Sockets (#692),
LittleFS (#693) and Zephyr (#694) — are deliberately left unmilestoned, so a
thumbs-up on one carries real signal about demand rather than being a reaction
to something already committed. Nothing in the repository told a reader that,
or where to go and do it.
Found as an uncommitted working-tree change with no branch behind it, predating
the TLS rework. It is unrelated to that work and is raised on its own so it
neither waits several weeks nor gets swept into an unrelated commit.
Change Description
One contact link added to the issue chooser, pointing at the open issues
carrying the
platformlabel, sorted by reactions. The sort matters: the listarrives already ordered by demand, so the most-wanted adapter is the first thing
a reader sees, and adding a vote is one click from there.
Placed below the two security routes and above commercial licensing. The free
way to influence what gets built should come before the paid one.
Test Evidence
No code, so no unit tests. Verified by hand:
platformlabel exists.E37: Zephyr platform support #694 — and nothing else, so it cannot present committed work as open to a
vote.
Areas Affected
.github/ISSUE_TEMPLATE/config.ymlalone. No library code, no documentationbuild, no derived projects.
blank_issues_enabledis unchanged, so the existingtemplates and the two security routes behave exactly as before.
Summary by CodeRabbit